System and method for accurately sensing user location in an IoT system

ABSTRACT

A system and method are described for accurately detecting a location of a wireless device. For example, one embodiment of a method comprises: collecting signal strength data indicating signal strength between a wireless device and a plurality of IoT devices and/or IoT hubs in a user&#39;s home; associating the signal strength data with locations in the user&#39;s home and storing the association in a location database; and determining a current location of the wireless device by comparing the signal strength data in the database with current signal strength data indicating current signal strength between the wireless device and the plurality of IoT devices and/or IoT hubs.

BACKGROUND

Field of the Invention

This invention relates generally to the field of computer systems. Moreparticularly, the invention relates to a system and method foraccurately sensing user location in an IoT system.

Description of the Related Art

The “Internet of Things” refers to the interconnection ofuniquely-identifiable embedded devices within the Internetinfrastructure. Ultimately, IoT is expected to result in new,wide-ranging types of applications in which virtually any type ofphysical thing may provide information about itself or its surroundingsand/or may be controlled remotely via client devices over the Internet.

IoT development and adoption has been slow due to issues related toconnectivity, power, and a lack of standardization. For example, oneobstacle to IoT development and adoption is that no standard platformexists to allow developers to design and offer new IoT devices andservices. In order enter into the IoT market, a developer must designthe entire IoT platform from the ground up, including the networkprotocols and infrastructure, hardware, software and services requiredto support the desired IoT implementation. As a result, each provider ofIoT devices uses proprietary techniques for designing and connecting theIoT devices, making the adoption of multiple types of IoT devicesburdensome for end users. Another obstacle to IoT adoption is thedifficulty associated with connecting and powering IoT devices.Connecting appliances such as refrigerators, garage door openers,environmental sensors, home security sensors/controllers, etc, forexample, requires an electrical source to power each connected IoTdevice, and such an electrical source is often not conveniently located.

Another problem which exists is that the wireless technologies used tointerconnect IoT devices such as Bluetooth LE are generally short rangetechnologies. Thus, if the data collection hub for an IoT implementationis outside the range of an IoT device, the IoT device will not be ableto transmit data to the IoT hub (and vice versa). Consequently,techniques are needed which would allow an IoT device to provide data toan IoT hub (or other IoT device) which is out of range.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained from thefollowing detailed description in conjunction with the followingdrawings, in which:

FIGS. 1A-B illustrates different embodiments of an IoT systemarchitecture;

FIG. 2 illustrates an IoT device in accordance with one embodiment ofthe invention;

FIG. 3 illustrates an IoT hub in accordance with one embodiment of theinvention;

FIGS. 4A-B illustrate embodiments of the invention for controlling andcollecting data from IoT devices, and generating notifications;

FIG. 5 illustrates embodiments of the invention for collecting data fromIoT devices and generating notifications from an IoT hub and/or IoTservice;

FIG. 6 illustrates problems with identifying a user in current wirelesslock systems;

FIG. 7 illustrates a system in which IoT devices and/or IoT hubs areemployed to accurately detect the location of a user of a wireless locksystem;

FIG. 8 illustrates another embodiment in which IoT devices and/or IoThubs are employed to accurately detect the location of a user of awireless lock system;

FIG. 9 illustrates one embodiment for calibrating a location detectionsystem and detecting a location of a user based on signal strengthvalues;

FIG. 10 illustrates a method for implementing a wireless lock systemusing IoT devices and/or IoT hubs;

FIG. 11 illustrates one embodiment of a method for calibrating awireless lock system;

FIG. 12 illustrates one embodiment of the invention for determining thelocation of a user with signal strength values;

FIG. 13 illustrates another embodiment for calibrating a locationdetection system and detecting a location of a user based on signalstrength values;

FIG. 14 illustrates embodiments of the invention which implementsimproved security techniques such as encryption and digital signatures;

FIG. 15 illustrates one embodiment of an architecture in which asubscriber identity module (SIM) is used to store keys on IoT devices;

FIG. 16A illustrates one embodiment in which IoT devices are registeredusing barcodes or QR codes;

FIG. 16B illustrates one embodiment in which pairing is performed usingbarcodes or QR codes;

FIG. 17 illustrates one embodiment of a method for programming a SIMusing an IoT hub;

FIG. 18 illustrates one embodiment of a method for registering an IoTdevice with an IoT hub and IoT service; and

FIG. 19 illustrates one embodiment of a method for encrypting data to betransmitted to an IoT device.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the embodiments of the invention described below. Itwill be apparent, however, to one skilled in the art that theembodiments of the invention may be practiced without some of thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form to avoid obscuring the underlyingprinciples of the embodiments of the invention.

One embodiment of the invention comprises an Internet of Things (IoT)platform which may be utilized by developers to design and build new IoTdevices and applications. In particular, one embodiment includes a basehardware/software platform for IoT devices including a predefinednetworking protocol stack and an IoT hub through which the IoT devicesare coupled to the Internet. In addition, one embodiment includes an IoTservice through which the IoT hubs and connected IoT devices may beaccessed and managed as described below. In addition, one embodiment ofthe IoT platform includes an IoT app or Web application (e.g., executedon a client device) to access and configured the IoT service, hub andconnected devices. Existing online retailers and other Website operatorsmay leverage the IoT platform described herein to readily provide uniqueIoT functionality to existing user bases.

FIG. 1A illustrates an overview of an architectural platform on whichembodiments of the invention may be implemented. In particular, theillustrated embodiment includes a plurality of IoT devices 101-105communicatively coupled over local communication channels 130 to acentral IoT hub 110 which is itself communicatively coupled to an IoTservice 120 over the Internet 220. Each of the IoT devices 101-105 mayinitially be paired to the IoT hub 110 (e.g., using the pairingtechniques described below) in order to enable each of the localcommunication channels 130. In one embodiment, the IoT service 120includes an end user database 122 for maintaining user accountinformation and data collected from each user's IoT devices. Forexample, if the IoT devices include sensors (e.g., temperature sensors,accelerometers, heat sensors, motion detectore, etc), the database 122may be continually updated to store the data collected by the IoTdevices 101-105. The data stored in the database 122 may then be madeaccessible to the end user via the IoT app or browser installed on theuser's device 135 (or via a desktop or other client computer system) andto web clients (e.g., such as websites 130 subscribing to the IoTservice 120).

The IoT devices 101-105 may be equipped with various types of sensors tocollect information about themselves and their surroundings and providethe collected information to the IoT service 120, user devices 135and/or external Websites 130 via the IoT hub 110. Some of the IoTdevices 101-105 may perform a specified function in response to controlcommands sent through the IoT hub 110. Various specific examples ofinformation collected by the IoT devices 101-105 and control commandsare provided below. In one embodiment described below, the IoT device101 is a user input device designed to record user selections and sendthe user selections to the IoT service 120 and/or Website.

In one embodiment, the IoT hub 110 includes a cellular radio toestablish a connection to the Internet 220 via a cellular service 115such as a 4G (e.g., Mobile WiMAX, LTE) or 5G cellular data service.Alternatively, or in addition, the IoT hub 110 may include a WiFi radioto establish a WiFi connection through a WiFi access point or router 116which couples the IoT hub 110 to the Internet (e.g., via an InternetService Provider providing Internet service to the end user). Of course,it should be noted that the underlying principles of the invention arenot limited to any particular type of communication channel or protocol.

In one embodiment, the IoT devices 101-105 are ultra low-power devicescapable of operating for extended periods of time on battery power(e.g., years). To conserve power, the local communication channels 130may be implemented using a low-power wireless communication technologysuch as Bluetooth Low Energy (LE). In this embodiment, each of the IoTdevices 101-105 and the IoT hub 110 are equipped with Bluetooth LEradios and protocol stacks.

As mentioned, in one embodiment, the IoT platform includes an IoT app orWeb application executed on user devices 135 to allow users to accessand configure the connected IoT devices 101-105, IoT hub 110, and/or IoTservice 120. In one embodiment, the app or web application may bedesigned by the operator of a Website 130 to provide IoT functionalityto its user base. As illustrated, the Website may maintain a userdatabase 131 containing account records related to each user.

FIG. 1B illustrates additional connection options for a plurality of IoThubs 110-111, 190 In this embodiment a single user may have multiplehubs 110-111 installed onsite at a single user premises 180 (e.g., theuser's home or business). This may be done, for example, to extend thewireless range needed to connect all of the IoT devices 101-105. Asindicated, if a user has multiple hubs 110, 111 they may be connectedvia a local communication channel (e.g., Wifi, Ethernet, Power LineNetworking, etc). In one embodiment, each of the hubs 110-111 mayestablish a direct connection to the IoT service 120 through a cellular115 or WiFi 116 connection (not explicitly shown in FIG. 1B).Alternatively, or in addition, one of the IoT hubs such as IoT hub 110may act as a “master” hub which provides connectivity and/or localservices to all of the other IoT hubs on the user premises 180, such asIoT hub 111 (as indicated by the dotted line connecting IoT hub 110 andIoT hub 111). For example, the master IoT hub 110 may be the only IoThub to establish a direct connection to the IoT service 120. In oneembodiment, only the “master” IoT hub 110 is equipped with a cellularcommunication interface to establish the connection to the IoT service120. As such, all communication between the IoT service 120 and theother IoT hubs 111 will flow through the master IoT hub 110. In thisrole, the master IoT hub 110 may be provided with additional programcode to perform filtering operations on the data exchanged between theother IoT hubs 111 and IoT service 120 (e.g., servicing some datarequests locally when possible).

Regardless of how the IoT hubs 110-111 are connected, in one embodiment,the IoT service 120 will logically associate the hubs with the user andcombine all of the attached IoT devices 101-105 under a singlecomprehensive user interface, accessible via a user device with theinstalled app 135 (and/or a browser-based interface).

In this embodiment, the master IoT hub 110 and one or more slave IoThubs 111 may connect over a local network which may be a WiFi network116, an Ethernet network, and/or a using power-line communications (PLC)networking (e.g., where all or portions of the network are run throughthe user's power lines). In addition, to the IoT hubs 110-111, each ofthe IoT devices 101-105 may be interconnected with the IoT hubs 110-111using any type of local network channel such as WiFi, Ethernet, PLC, orBluetooth LE, to name a few.

FIG. 1B also shows an IoT hub 190 installed at a second user premises181. A virtually unlimited number of such IoT hubs 190 may be installedand configured to collect data from IoT devices 191-192 at user premisesaround the world. In one embodiment, the two user premises 180-181 maybe configured for the same user. For example, one user premises 180 maybe the user's primary home and the other user premises 181 may be theuser's vacation home. In such a case, the IoT service 120 will logicallyassociate the IoT hubs 110-111, 190 with the user and combine all of theattached IoT devices 101-105, 191-192 under a single comprehensive userinterface, accessible via a user device with the installed app 135(and/or a browser-based interface).

As illustrated in FIG. 2, an exemplary embodiment of an IoT device 101includes a memory 210 for storing program code and data 201-203 and alow power microcontroller 200 for executing the program code andprocessing the data. The memory 210 may be a volatile memory such asdynamic random access memory (DRAM) or may be a non-volatile memory suchas Flash memory. In one embodiment, a non-volatile memory may be usedfor persistent storage and a volatile memory may be used for executionof the program code and data at runtime. Moreover, the memory 210 may beintegrated within the low power microcontroller 200 or may be coupled tothe low power microcontroller 200 via a bus or communication fabric. Theunderlying principles of the invention are not limited to any particularimplementation of the memory 210.

As illustrated, the program code may include application program code203 defining an application-specific set of functions to be performed bythe IoT device 201 and library code 202 comprising a set of predefinedbuilding blocks which may be utilized by the application developer ofthe IoT device 101. In one embodiment, the library code 202 comprises aset of basic functions required to implement an IoT device such as acommunication protocol stack 201 for enabling communication between eachIoT device 101 and the IoT hub 110. As mentioned, in one embodiment, thecommunication protocol stack 201 comprises a Bluetooth LE protocolstack. In this embodiment, Bluetooth LE radio and antenna 207 may beintegrated within the low power microcontroller 200. However, theunderlying principles of the invention are not limited to any particularcommunication protocol.

The particular embodiment shown in FIG. 2 also includes a plurality ofinput devices or sensors 210 to receive user input and provide the userinput to the low power microcontroller, which processes the user inputin accordance with the application code 203 and library code 202. In oneembodiment, each of the input devices include an LED 209 to providefeedback to the end user.

In addition, the illustrated embodiment includes a battery 208 forsupplying power to the low power microcontroller. In one embodiment, anon-chargeable coin cell battery is used. However, in an alternateembodiment, an integrated rechargeable battery may be used (e.g.,rechargeable by connecting the IoT device to an AC power supply (notshown)).

A speaker 205 is also provided for generating audio. In one embodiment,the low power microcontroller 299 includes audio decoding logic fordecoding a compressed audio stream (e.g., such as an MPEG-4/AdvancedAudio Coding (AAC) stream) to generate audio on the speaker 205.Alternatively, the low power microcontroller 200 and/or the applicationcode/data 203 may include digitally sampled snippets of audio to provideverbal feedback to the end user as the user enters selections via theinput devices 210.

In one embodiment, one or more other/alternate I/O devices or sensors250 may be included on the IoT device 101 based on the particularapplication for which the IoT device 101 is designed. For example, anenvironmental sensor may be included to measure temperature, pressure,humidity, etc. A security sensor and/or door lock opener may be includedif the IoT device is used as a security device. Of course, theseexamples are provided merely for the purposes of illustration. Theunderlying principles of the invention are not limited to any particulartype of IoT device. In fact, given the highly programmable nature of thelow power microcontroller 200 equipped with the library code 202, anapplication developer may readily develop new application code 203 andnew I/O devices 250 to interface with the low power microcontroller forvirtually any type of IoT application.

In one embodiment, the low power microcontroller 200 also includes asecure key store for storing encryption keys for encryptingcommunications and/or generating signatures. Alternatively, the keys maybe secured in a subscriber identity module (SIM).

A wakeup receiver 207 is included in one embodiment to wake the IoTdevice from an ultra low power state in which it is consuming virtuallyno power. In one embodiment, the wakeup receiver 207 is configured tocause the IoT device 101 to exit this low power state in response to awakeup signal received from a wakeup transmitter 307 configured on theIoT hub 110 as shown in FIG. 3. In particular, in one embodiment, thetransmitter 307 and receiver 207 together form an electrical resonanttransformer circuit such as a Tesla coil. In operation, energy istransmitted via radio frequency signals from the transmitter 307 to thereceiver 207 when the hub 110 needs to wake the IoT device 101 from avery low power state. Because of the energy transfer, the IoT device 101may be configured to consume virtually no power when it is in its lowpower state because it does not need to continually “listen” for asignal from the hub (as is the case with network protocols which allowdevices to be awakened via a network signal). Rather, themicrocontroller 200 of the IoT device 101 may be configured to wake upafter being effectively powered down by using the energy electricallytransmitted from the transmitter 307 to the receiver 207.

As illustrated in FIG. 3, the IoT hub 110 also includes a memory 317 forstoring program code and data 305 and hardware logic 301 such as amicrocontroller for executing the program code and processing the data.A wide area network (WAN) interface 302 and antenna 310 couple the IoThub 110 to the cellular service 115. Alternatively, as mentioned above,the IoT hub 110 may also include a local network interface (not shown)such as a WiFi interface (and WiFi antenna) or Ethernet interface forestablishing a local area network communication channel. In oneembodiment, the hardware logic 301 also includes a secure key store forstoring encryption keys for encrypting communications andgenerating/verifying signatures. Alternatively, the keys may be securedin a subscriber identify module (SIM).

A local communication interface 303 and antenna 311 establishes localcommunication channels with each of the IoT devices 101-105. Asmentioned above, in one embodiment, the local communication interface303/antenna 311 implements the Bluetooth LE standard. However, theunderlying principles of the invention are not limited to any particularprotocols for establishing the local communication channels with the IoTdevices 101-105. Although illustrated as separate units in FIG. 3, theWAN interface 302 and/or local communication interface 303 may beembedded within the same chip as the hardware logic 301.

In one embodiment, the program code and data includes a communicationprotocol stack 308 which may include separate stacks for communicatingover the local communication interface 303 and the WAN interface 302. Inaddition, device pairing program code and data 306 may be stored in thememory to allow the IoT hub to pair with new IoT devices. In oneembodiment, each new IoT device 101-105 is assigned a unique code whichis communicated to the IoT hub 110 during the pairing process. Forexample, the unique code may be embedded in a barcode on the IoT deviceand may be read by the barcode reader 106 or may be communicated overthe local communication channel 130. In an alternate embodiment, theunique ID code is embedded magnetically on the IoT device and the IoThub has a magnetic sensor such as an radio frequency ID (RFID) or nearfield communication (NFC) sensor to detect the code when the IoT device101 is moved within a few inches of the IoT hub 110.

In one embodiment, once the unique ID has been communicated, the IoT hub110 may verify the unique ID by querying a local database (not shown),performing a hash to verify that the code is acceptable, and/orcommunicating with the IoT service 120, user device 135 and/or Website130 to validate the ID code. Once validated, in one embodiment, the IoThub 110 pairs the IoT device 101 and stores the pairing data in memory317 (which, as mentioned, may include non-volatile memory). Once pairingis complete, the IoT hub 110 may connect with the IoT device 101 toperform the various IoT functions described herein.

In one embodiment, the organization running the IoT service 120 mayprovide the IoT hub 110 and a basic hardware/software platform to allowdevelopers to easily design new IoT services. In particular, in additionto the IoT hub 110, developers may be provided with a softwaredevelopment kit (SDK) to update the program code and data 305 executedwithin the hub 110. In addition, for IoT devices 101, the SDK mayinclude an extensive set of library code 202 designed for the base IoThardware (e.g., the low power microcontroller 200 and other componentsshown in FIG. 2) to facilitate the design of various different types ofapplications 101. In one embodiment, the SDK includes a graphical designinterface in which the developer needs only to specify input and outputsfor the IoT device. All of the networking code, including thecommunication stack 201 that allows the IoT device 101 to connect to thehub 110 and the service 120, is already in place for the developer. Inaddition, in one embodiment, the SDK also includes a library code baseto facilitate the design of apps for mobile devices (e.g., iPhone andAndroid devices).

In one embodiment, the IoT hub 110 manages a continuous bi-directionalstream of data between the IoT devices 101-105 and the IoT service 120.In circumstances where updates to/from the IoT devices 101-105 arerequired in real time (e.g., where a user needs to view the currentstatus of security devices or environmental readings), the IoT hub maymaintain an open TCP socket to provide regular updates to the userdevice 135 and/or external Websites 130. The specific networkingprotocol used to provide updates may be tweaked based on the needs ofthe underlying application. For example, in some cases, where may notmake sense to have a continuous bi-directional stream, a simplerequest/response protocol may be used to gather information when needed.

In one embodiment, both the IoT hub 110 and the IoT devices 101-105 areautomatically upgradeable over the network. In particular, when a newupdate is available for the IoT hub 110 it may automatically downloadand install the update from the IoT service 120. It may first copy theupdated code into a local memory, run and verify the update beforeswapping out the older program code. Similarly, when updates areavailable for each of the IoT devices 101-105, they may initially bedownloaded by the IoT hub 110 and pushed out to each of the IoT devices101-105. Each IoT device 101-105 may then apply the update in a similarmanner as described above for the IoT hub and report back the results ofthe update to the IoT hub 110. If the update is successful, then the IoThub 110 may delete the update from its memory and record the latestversion of code installed on each IoT device (e.g., so that it maycontinue to check for new updates for each IoT device).

In one embodiment, the IoT hub 110 is powered via A/C power. Inparticular, the IoT hub 110 may include a power unit 390 with atransformer for transforming A/C voltage supplied via an A/C power cordto a lower DC voltage.

FIG. 4A illustrates one embodiment of the invention for performinguniversal remote control operations using the IoT system. In particular,in this embodiment, a set of IoT devices 101-103 are equipped withinfrared (IR) and/or radio frequency (RF) blasters 401-403,respectively, for transmitting remote control codes to control variousdifferent types of electronics equipment including airconditioners/heaters 430, lighting systems 431, and audiovisualequipment 432 (to name just a few). In the embodiment shown in FIG. 4A,the IoT devices 101-103 are also equipped with sensors 404-406,respectively, for detecting the operation of the devices which theycontrol, as described below.

For example, sensor 404 in IoT device 101 may be a temperature and/orhumidity sensor for sensing the current temperature/humidity andresponsively controlling the air conditioner/heater 430 based on acurrent desired temperature. In this embodiment, the airconditioner/heater 430 is one which is designed to be controlled via aremote control device (typically a remote control which itself has atemperature sensor embedded therein). In one embodiment, the userprovides the desired temperature to the IoT hub 110 via an app orbrowser installed on a user device 135. Control logic 412 executed onthe IoT hub 110 receives the current temperature/humidity data from thesensor 404 and responsively transmits commands to the IoT device 101 tocontrol the IR/RF blaster 401 in accordance with the desiredtemperature/humidity. For example, if the temperature is below thedesired temperature, then the control logic 412 may transmit a commandto the air conditioner/heater via the IR/RF blaster 401 to increase thetemperature (e.g., either by turning off the air conditioner or turningon the heater). The command may include the necessary remote controlcode stored in a database 413 on the IoT hub 110. Alternatively, or inaddition, the IoT service 421 may implement control logic 421 to controlthe electronics equipment 430-432 based on specified user preferencesand stored control codes 422.

IoT device 102 in the illustrated example is used to control lighting431. In particular, sensor 405 in IoT device 102 may photosensor orphotodetector configured to detect the current brightness of the lightbeing produced by a light fixture 431 (or other lighting apparatus). Theuser may specify a desired lighting level (including an indication of ONor OFF) to the IoT hub 110 via the user device 135. In response, thecontrol logic 412 will transmit commands to the IR/RF blaster 402 tocontrol the current brightness level of the lights 431 (e.g., increasingthe lighting if the current brightness is too low or decreasing thelighting if the current brightness is too high; or simply turning thelights ON or OFF).

IoT device 103 in the illustrated example is configured to controlaudiovisual equipment 432 (e.g., a television, A/V receiver,cable/satellite receiver, AppleTV™, etc). Sensor 406 in IoT device 103may be an audio sensor (e.g., a microphone and associated logic) fordetecting a current ambient volume level and/or a photosensor to detectwhether a television is on or off based on the light generated by thetelevision (e.g., by measuring the light within a specified spectrum).Alternatively, sensor 406 may include a temperature sensor connected tothe audiovisual equipment to detect whether the audio equipment is on oroff based on the detected temperature. Once again, in response to userinput via the user device 135, the control logic 412 may transmitcommands to the audiovisual equipment via the IR blaster 403 of the IoTdevice 103.

It should be noted that the foregoing are merely illustrative examplesof one embodiment of the invention. The underlying principles of theinvention are not limited to any particular type of sensors or equipmentto be controlled by IoT devices.

In an embodiment in which the IoT devices 101-103 are coupled to the IoThub 110 via a Bluetooth LE connection, the sensor data and commands aresent over the Bluetooth LE channel. However, the underlying principlesof the invention are not limited to Bluetooth LE or any othercommunication standard.

In one embodiment, the control codes required to control each of thepieces of electronics equipment are stored in a database 413 on the IoThub 110 and/or a database 422 on the IoT service 120. As illustrated inFIG. 4B, the control codes may be provided to the IoT hub 110 from amaster database of control codes 422 for different pieces of equipmentmaintained on the IoT service 120. The end user may specify the types ofelectronic (or other) equipment to be controlled via the app or browserexecuted on the user device 135 and, in response, a remote control codelearning module 491 on the IoT hub may retrieve the required IR/RF codesfrom the remote control code database 492 on the IoT service 120 (e.g.,identifying each piece of electronic equipment with a unique ID).

In addition, in one embodiment, the IoT hub 110 is equipped with anIR/RF interface 490 to allow the remote control code learning module 491to “learn” new remote control codes directly from the original remotecontrol 495 provided with the electronic equipment. For example, ifcontrol codes for the original remote control provided with the airconditioner 430 is not included in the remote control database, the usermay interact with the IoT hub 110 via the app/browser on the user device135 to teach the IoT hub 110 the various control codes generated by theoriginal remote control (e.g., increase temperature, decreasetemperature, etc). Once the remote control codes are learned they may bestored in the control code database 413 on the IoT hub 110 and/or sentback to the IoT service 120 to be included in the central remote controlcode database 492 (and subsequently used by other users with the sameair conditioner unit 430).

In one embodiment, each of the IoT devices 101-103 have an extremelysmall form factor and may be affixed on or near their respectiveelectronics equipment 430-432 using double-sided tape, a small nail, amagnetic attachment, etc. For control of a piece of equipment such asthe air conditioner 430, it would be desirable to place the IoT device101 sufficiently far away so that the sensor 404 can accurately measurethe ambient temperature in the home (e.g., placing the IoT devicedirectly on the air conditioner would result in a temperaturemeasurement which would be too low when the air conditioner was runningor too high when the heater was running). In contrast, the IoT device102 used for controlling lighting may be placed on or near the lightingfixture 431 for the sensor 405 to detect the current lighting level.

In addition to providing general control functions as described, oneembodiment of the IoT hub 110 and/or IoT service 120 transmitsnotifications to the end user related to the current status of eachpiece of electronics equipment. The notifications, which may be textmessages and/or app-specific notifications, may then be displayed on thedisplay of the user's mobile device 135. For example, if the user's airconditioner has been on for an extended period of time but thetemperature has not changed, the IoT hub 110 and/or IoT service 120 maysend the user a notification that the air conditioner is not functioningproperly. If the user is not home (which may be detected via motionsensors or based on the user's current detected location), and thesensors 406 indicate that audiovisual equipment 430 is on or sensors 405indicate that the lights are on, then a notification may be sent to theuser, asking if the user would like to turn off the audiovisualequipment 432 and/or lights 431. The same type of notification may besent for any equipment type.

Once the user receives a notification, he/she may remotely control theelectronics equipment 430-432 via the app or browser on the user device135. In one embodiment, the user device 135 is a touchscreen device andthe app or browser displays an image of a remote control withuser-selectable buttons for controlling the equipment 430-432. Uponreceiving a notification, the user may open the graphical remote controland turn off or adjust the various different pieces of equipment. Ifconnected via the IoT service 120, the user's selections may beforwarded from the IoT service 120 to the IoT hub 110 which will thencontrol the equipment via the control logic 412. Alternatively, the userinput may be sent directly to the IoT hub 110 from the user device 135.

In one embodiment, the user may program the control logic 412 on the IoThub 110 to perform various automatic control functions with respect tothe electronics equipment 430-432. In addition to maintaining a desiredtemperature, brightness level, and volume level as described above, thecontrol logic 412 may automatically turn off the electronics equipmentif certain conditions are detected. For example, if the control logic412 detects that the user is not home and that the air conditioner isnot functioning, it may automatically turn off the air conditioner.Similarly, if the user is not home, and the sensors 406 indicate thataudiovisual equipment 430 is on or sensors 405 indicate that the lightsare on, then the control logic 412 may automatically transmit commandsvia the IR/RF blasters 403 and 402, to turn off the audiovisualequipment and lights, respectively.

FIG. 5 illustrates additional embodiments of IoT devices 104-105equipped with sensors 503-504 for monitoring electronic equipment530-531. In particular, the IoT device 104 of this embodiment includes atemperature sensor 503 which may be placed on or near a stove 530 todetect when the stove has been left on. In one embodiment, the IoTdevice 104 transmits the current temperature measured by the temperaturesensor 503 to the IoT hub 110 and/or the IoT service 120. If the stoveis detected to be on for more than a threshold time period (e.g., basedon the measured temperature), then control logic 512 may transmit anotification to the end user's device 135 informing the user that thestove 530 is on. In addition, in one embodiment, the IoT device 104 mayinclude a control module 501 to turn off the stove, either in responseto receiving an instruction from the user or automatically (if thecontrol logic 512 is programmed to do so by the user). In oneembodiment, the control logic 501 comprises a switch to cut offelectricity or gas to the stove 530. However, in other embodiments, thecontrol logic 501 may be integrated within the stove itself.

FIG. 5 also illustrates an IoT device 105 with a motion sensor 504 fordetecting the motion of certain types of electronics equipment such as awasher and/or dryer. Another sensor that may be used is an audio sensor(e.g., microphone and logic) for detecting an ambient volume level. Aswith the other embodiments described above, this embodiment may transmitnotifications to the end user if certain specified conditions are met(e.g., if motion is detected for an extended period of time, indicatingthat the washer/dryer are not turning off). Although not shown in FIG.5, IoT device 105 may also be equipped with a control module to turn offthe washer/dryer 531 (e.g., by switching off electric/gas),automatically, and/or in response to user input.

In one embodiment, a first IoT device with control logic and a switchmay be configured to turn off all power in the user's home and a secondIoT device with control logic and a switch may be configured to turn offall gas in the user's home. IoT devices with sensors may then bepositioned on or near electronic or gas-powered equipment in the user'shome. If the user is notified that a particular piece of equipment hasbeen left on (e.g., the stove 530), the user may then send a command toturn off all electricity or gas in the home to prevent damage.Alternatively, the control logic 512 in the IoT hub 110 and/or the IoTservice 120 may be configured to automatically turn off electricity orgas in such situations.

In one embodiment, the IoT hub 110 and IoT service 120 communicate atperiodic intervals. If the IoT service 120 detects that the connectionto the IoT hub 110 has been lost (e.g., by failing to receive a requestor response from the IoT hub for a specified duration), it willcommunicate this information to the end user's device 135 (e.g., bysending a text message or app-specific notification).

Apparatus and Method for Accurately Sensing User Location in an IoTSystem

Current wireless “smart” locks and garage door openers allow an end userto control a lock and/or garage door via a mobile device. To operatethese systems, the user must open an app on the mobile device and selectan open/unlock or close/lock option. In response, a wireless signal issent to a receiver on or coupled to the wireless lock or garage doorwhich implements the desired operation. While the discussion belowfocuses on wireless “locks”, the term “lock” is used broadly herein torefer to standard door locks, wireless garage door openers, and anyother device for limiting access to a building or other location.

Some wireless locks attempt to determine when the user is outside thedoor and responsively trigger the open/unlock function. FIG. 6, forexample, illustrates an example in which a wireless lock 602 istriggered in response to a user with a wireless device 603 approachingfrom the outside of the door 601, based on the signal strength of thesignal from the wireless device 603. For example, the wireless lock 602may measure the received signal strength indicator (RSSI) from thewireless device 603 and, when it reaches a threshold (e.g., −60 dbm),will unlock the door 601.

One obvious problem with these techniques is that the RSSI measurementis non-directional. For example, the user may move around the home withthe wireless device 603 and pass by the wireless lock 602 or garage dooropener, thereby causing it to trigger. For this reason, the use ofwireless locks which operate based on user proximity detection has beenlimited.

FIG. 7 illustrates one embodiment of the invention which an IoT huband/or IoT device 710 is used to determine the location of the user withgreater accuracy. In particular, this embodiment of the inventionmeasures signal strength between the wireless device 703 and the IoTlock device 702 and also measures signal strength between the wirelessdevice 703 and one or more IoT devices/hubs 710 to differentiate betweencases where the user is outside the home and inside the home. Forexample, if the user is a particular distance from the IoT lock 702inside or outside the home, then the signal strength 761 from theposition inside the home and signal strength 760 outside the home may beroughly the same. In prior systems, such as illustrated in FIG. 6, therewas no way to differentiate between these two cases. However, in theembodiment shown in FIG. 7, the differences in signal strengthmeasurements 750 and 751, measured between the IoT hub/device 710 andthe wireless device 703 when the user is outside the home and inside thehome, respectively, are used to determine the location of the user. Forexample, when the wireless device 703 is at the outside location, thesignal strength 750 may be measurably different than the signal strength751 when the wireless device 703 is at the inside location. While inmost cases the signal strength 751 inside the home should be stronger,there may be instances where the signal strength 751 is actually weaker.The important point is that the signal strength may be used todifferentiate the two positions.

The signal strength values 760-761, 750-751 may be evaluated at the IoThub/device 710 or at the IoT lock 702 (if it has the intelligence toperform this evaluation). The remainder of this discussion will assumethat the signal strength evaluation is performed by an IoT hub 710,which may then transmit a lock or unlock command (or no command ifalready locked/unlocked) to the IoT lock 702 over a wirelesscommunication channel 770 (e.g., BTLE) based on the results of theevaluation. It should be noted, however that the same basic evaluationand result may be performed directly by the IoT lock 702 if it isconfigured with the logic to perform the evaluation (e.g., where thesignal strength values are provided to the IoT lock 702).

FIG. 8 illustrates another embodiment which is capable of providinggreater accuracy, because it utilizes the signal strength values fromtwo IoT hubs/devices 710-711. In this embodiment, the signal strength805 is measured between the wireless device 703 and (1) IoT hub/device711; (2) IoT hub/device 710; and (3) IoT lock 702. The wireless deviceis shown in a single position in FIG. 8 for simplicity.

In one embodiment, all of the collected signal strength values areprovided to one of the IoT hub devices 710-711, which then evaluate thevalues to determine the location of the user (e.g., inside or outside).If it is determined that the user is outside, then the IoT hub/device710 may send a command to the IoT lock 702 to unlock the door.Alternatively, if the IoT lock 702 has the logic to perform theevaluation, the IoT hubs/devices 710-711 may transmit the signalstrength values to the IoT lock 702 which evaluates the signal strengthvalues to determine the location of the user.

As illustrated in FIG. 9, in one embodiment, a calibration module 910 onthe IoT hub 710 communicates with an app or browser-based code on thewireless device 703 to calibrate the signal strength measurements.During calibration, the system calibration module 910 and/or calibrationapp may instruct the user to stand in certain locations outside the doorand inside the door (e.g., outside 6 ft outside door 1, 6 ft inside door1, 6 ft outside door 2, etc). The user may indicate that he/she is inthe desired position by selecting a graphic on the user interface. Thesystem calibration app and/or system calibration module 910 will thenassociate the collected signal strength values 900 with each locationwithin a location database 901 on the IoT hub/device 710.

Once the signal strength values for different known locations of theuser are collected and stored in the database 901, a signal strengthanalysis module 911 uses these values to determine whether to send IoTlock commands 950 to lock/unlock the door based on the detected signalstrength values. In the embodiment shown in FIG. 9, four exemplarylocations are shown for two different doors: outside door 1, inside door1, outside door 2, and inside door 2. The RSSI1 value is associated withthe wireless lock and is set to a threshold value of −60 dbm. Thus, inone embodiment, the signal strength analysis module 911 will not performits evaluation to determine the location of the user unless the RSSI1value is at least −60 dmb. The RSSI2 and RSSI3 values are signalstrength values measured between the user's wireless device and twodifferent IoT hubs/devices.

Assuming that the RSSI1 threshold is reached, the signal strengthanalysis module 911 compares the current signal strength values 900measured between the IoT hubs/devices and the user's wireless devicewith the RSSI2/RSSI3 values from the location database 901. If thecurrent RSSI values are within a specified range of the values specifiedin the database for RSSI2 (e.g., for IoT hub/device 710) and RSSI3 (e.g.for IoT hub/device 711), then the wireless device is determined to be ator near the associated location. For example, because the RSSI2 valueassociated with the “outside door 1” location is −90 dbm (e.g., based onthe measurement made during calibration), if the currently measuredsignal strength for RSSI2 is between −93 dbm and −87 dbm then the RSSI2comparison may be verified (assuming a specified range of ±3 dbm).Similarly, because the RSSI3 value associated with the “outside door 1”location is −85 dbm (e.g., based on the measurement made duringcalibration), if the currently measured signal strength for RSSI3 isbetween −88 dbm and −82 dbm then the RSSI3 comparison may be verified.Thus, if the user is within the −60 dbm value for the IoT lock andwithin the above-specified ranges for RSSI2 and RSSI3, the signalstrength analysis module 911 will send a command 950 to open the lock.By comparing the different RSSI values in this manner, the system avoidsundesirable “unlock” events when the user passes within −60 dbm of theIoT lock from inside the home, because the RSSI measurements for RSSI2and RSSI3 are used to differentiate the inside and outside cases.

In one embodiment, the signal strength analysis module 911 relies on onRSSI values which provide the greatest amount of differentiation betweenthe inside and outside cases. For example, there may be some instanceswhere the RSSI values for the inside and outside cases are equivalent orvery close (e.g., such as the RSSI3 values of −96 dbm and −97 dbm forinside door 2 and outside door 2, respectively). In such a case, thesignal strength analysis module will use the other RSSI value todifferentiate the two cases. In addition, in one embodiment, the signalstrength analysis module 911 may dynamically adjust the RSSI ranges usedfor the comparison when the recorded RSSI values are close (e.g., makingthe ranges smaller when the measured RSSI values are closer). Thus,while ±3 dbm is used as a comparison range for the example above,various different ranges may be set for the comparison based on the howclose the RSSI measurements are.

In one embodiment, the system calibration module 910 system continues totrain the system by measuring dbm values each time the user entersthrough a door. For example, in response to the user successfullyentering the home following the initial calibration, the systemcalibration module 910 may store additional RSSI values for RSSI2 andRSSI3. In this manner, a range of RSSI values may be stored for eachcase in the location/signal strength database 901 to furtherdifferentiate between the inside and outside cases. The end result is afar more accurate wireless lock system than currently available.

A method in accordance with one embodiment of the invention isillustrated in FIG. 10. The method may be implemented within the contextof the system architectures described above, but is not limited to anyspecific system architecture.

At 1001, the wireless signals strength between a user device and an IoTlock is measured. At 1002, if the signal strength is above a specifiedthreshold (i.e., indicating that the user is near the door), then at1002, the wireless signal strength between the user device and one ormore IoT hubs/devices is measured. At 1003, the collected wirelesssignal strength values are compared with previously collected and storedsignal strength values to determine the location of the user. Forexample, if the RSSI values are within a specified range of RSSI valueswhen the user was previously outside of the door, then it may bedetermined that the user is presently outside of the door. At 1004,based on the evaluation, a determination is made as to whether the useris outside of the door. If so, then at 1005, the door is automaticallyunlocked using the IoT lock.

A method for calibrating the IoT lock system is illustrated in FIG. 11.At 1101, the user is asked to stand outside of the door and at 1102, thewireless signal strength data is collected between the user device andone or more IoT devices/hubs. As mentioned, the request may be sent tothe user via a user app installed on the user's wireless device. At1103, the user is asked to stand inside of the door and at 1104, thewireless signal strength data is collected between the user device andthe IoT devices/hubs. At 1105, the signal strength data is stored in adatabase so that it may be used to compare signal strength values asdescribed herein to determine the user's current location.

Note that while a user's home is used herein as an exemplary embodiment,the embodiments of the invention are not limited to a consumerapplication. For example, these same techniques may be employed toprovide access to businesses or other types of buildings.

In one embodiment, similar techniques as described above are used totrack the user throughout the user's home. For example, by tracking theRSSI measurements between the user's wireless device and various IoTdevices/hubs in the user's home, a “map” of different user locations maybe compiled. This map may then be used to provide services to the enduser, such as directing audio to speakers in the room in which the useris presently located.

FIG. 12 provides an overview of an exemplary system in which RSSI valuesmeasured between the wireless device 703 and a plurality of IoT devices1101-1105 and IoT hub 1110 are used to determine whether the user is inRooms A, B, or C. In particular, based on the RSSI values 1121-1123measured between the wireless device 703 and the IoT hub 1110, IoTdevice 1103, and IoT device 1102, the IoT hub 1110 may determine thatthe user is presently in Room B, as illustrated. Similarly, when theuser moves into Room C, RSSI measurements between the wireless device703 and IoT devices 1104-1105 and IoT hub 1110 may then be used todetermine that the user is in Room C. While only 3 RSSI measurements1121-1123 are shown in FIG. 12, RSSI measurements may be made betweenany IoT device or IoT hub within range of the wireless device 703 toprovide greater accuracy.

In one embodiment, the IoT hub 1110 may employ triangulation techniquesbased on RSSI values between itself and the various IoT devices1101-1105 and the wireless device 703 to triangulate the location of theuser. For example, the RSSI triangle formed between IoT device 1102, theIoT hub 1110 and the wireless device 703 may be used to determine thepresent location of the wireless device 703, based on the RSSI valuesfor each edge of the triangle.

In one embodiment, similar calibration techniques to those describedabove may be used to collect signal strength values in each room. FIG.13 illustrates the system calibration module 910 which, as in theembodiments described above, communicates with an app or browser-basedcode on the wireless device 703 to calibrate the signal strengthmeasurements. During calibration, the system calibration module 910and/or calibration app may instruct the user to stand in different roomsand in certain locations within each room, depending on the applicationsfor which the IoT system is being used. As described above, the user mayindicate that he/she is in the desired position by selecting a graphicon the user interface. The system calibration app and/or systemcalibration module 910 will then associate the collected signal strengthvalues 900 with each location within a location database 1301 on the IoThub/device 710.

Once the signal strength values for different known locations of theuser are collected and stored in the database 1301, a signal strengthanalysis module 911 uses these values to control the various IoT devices1101-1105 around the user's home. For example, if the IoT devices1101-1105 comprise speakers or amplifiers for a home audio system, thesignal strength analysis module 911 may transmit IoT device commands1302 to control the rooms in which the audio is being played back (e.g.,turning on speakers in the room in which the user is present and turningoff speakers in other rooms). Similarly, if the IoT devices 1101-1105comprise lighting control units, then the signal strength analysismodule 911 may transmit IoT device commands 1302 to turn on lights inthe room in which the user is present and turn off lights in the otherrooms. Of course, the underlying principles of the invention are notlimited to any specific end-user applications.

As mentioned, one embodiment of the system calibration module 910 willcollect RSSI data for different points within a room based on theapplication. In FIG. 13, RSSI ranges are collected for each room byinstructing the user to stand in different positions within the room.For example, for the user's Family Room, RSSI ranges of −99 dbm to −93dbm, −111 dbm to −90 dbm and −115 dbm to −85 dbm are collected forRSSI1, RSSI2, and RSSI3, respectively (i.e., collected from threedifferent IoT devices/hubs). When the current position of the wirelessdevice 703 falls within each of these ranges, the signal strengthanalysis module 911 will determine that the user is in the Family Roomand potentially send IoT device commands 1302 to perform a specified setof functions (e.g., turn on lights, audio, etc). In addition, forspecific points within the room, specific RSSI values may be collected.For example, in FIG. 13, values of −88 dbm, −99 dbm, and −101 dbm havebeen collected when the user is sitting on the sofa in the family room.As in the embodiments described above, the signal strength analysismodule 911 may determine that the user is on the couch if the RSSIvalues are within a specified range of the stored RSSI values (e.g.,within while ±3 dbm). In addition, as in prior embodiments, the systemcalibration module 910 may continue to collect data for the differentlocations to ensure that the RSSI values remain current. For example, ifthe user rearranges the Family Room, the position of the couch may move.In this case, the system calibration module 910 may ask the user if theuser is currently sitting the couch (e.g., given the similarity of theRSSI values from those stored in the database), and update the signalstrength database 1301 with the new values.

In one embodiment, the user's interaction with various types of IoTdevices may be used to determine the location of the user. For example,if the user's refrigerator is equipped with an IoT device, then thesystem may take RSSI measurements upon detecting that the user hasopened the refrigerator door. Similarly, if the lighting systemcomprises an IoT system, when the user adjusts the lights in differentrooms of the home or business, the system may automatically take RSSImeasurements. By way of another example, when the user interacts withvarious appliances (e.g., washers, dryers, dishwasher), audiovisualequipment (e.g., televisions, audio equipment, etc), or HVAC systems(e.g., adjusting the thermostat), the system may capture RSSImeasurements and associate the measurements with these locations.

While a single user is described in the embodiments set forth above, theembodiments of the invention may be implemented for multiple users. Forexample, the system calibration module 910 may collect signal strengthvalues for both User A and User B to be stored in the signal strengthdatabase 1301. The signal strength analysis module 911 may then identifythe current location of Users A and B based on comparisons of signalstrength measurements and send IoT commands 1302 to control IoT devicesaround the home of Users A and B (e.g., keeping on lights/speakers inthe rooms in which Users A and B are present).

The wireless device 703 employed in the embodiments of the inventiondescribed herein may be a smartphone, tablet, wearable device (e.g., asmartwatch, token on a neckless or bracelet), or any other form ofwireless device 703 capable of detecting RSSI values. In one embodiment,the wireless device 703 communicates with the IoT devices 1101-1105 andIoT hub 1110 via a short range, low power wireless communicationprotocol such as Bluetooth LE (BTLE). In addition, in one embodiment,the wireless device 703 communicates with the IoT hub 1110 via a longerrange wireless protocol such as Wifi. Thus, in this embodiment, the RSSIvalues may be gathered by the wireless device 703 and communicated backto the IoT hub 1110 using the longer range protocol. In addition, eachof the individual IoT devices 1101-1105 may collect the RSSI values andcommunicate these values back to the IoT hub 1110 via the short rangewireless protocol. The underlying principles of the invention are notlimited to any specific protocol or technique used to collect the RSSIvalues.

One embodiment of the invention uses the techniques described herein tolocate an ideal position for a wireless extender to extend the range ofthe IoT hub 1110 using the short range wireless protocol. For example,in one embodiment, upon purchasing a new extender the system calibrationmodule 910 will send instructions for the user to move into each of therooms of the user's home with the wireless extender device (e.g., bysending instructions to the app on the wireless device 703). Aconnection wizard may also be executed on the wireless device 703 tostep the user through the process. Following the instructions sent bythe system calibration module 910 or from the wizard, the user will walkinto each room and press a button on the wireless device 703. The IoThub 1110 will then measure signal strength between itself and theextender and also the signal strength between the extender and all ofthe other IoT devices in the system. The system calibration module 910or wireless device wizard may then provide the user will a prioritizedlist of the best locations to place the wireless extender (i.e.,selecting those locations with the highest signal strength between thewireless extender and the IoT hub 1110 and/or between the wirelessextender and the IoT devices 1101-1105).

The embodiments of the invention described above provide for fine-tunedlocation awareness within an IoT system not found in current IoTsystems. In addition, to improve location accuracy, in one embodimentthe GPS system on the wireless device 703 may communicate precise GPSdata to be used to provide an accurate map of the user's home which willinclude GPS data as well as RSSI data for each location.

Embodiments for Improved Security

In one embodiment, the low power microcontroller 200 of each IoT device101 and the low power logic/microcontroller 301 of the IoT hub 110include a secure key store for storing encryption keys used by theembodiments described below (see, e.g., FIGS. 14-19 and associatedtext). Alternatively, the keys may be secured in a subscriber identitymodule (SIM) as discussed below.

FIG. 14 illustrates a high level architecture which uses public keyinfrastructure (PKI) techniques and/or symmetric key exchange/encryptiontechniques to encrypt communications between the IoT Service 120, theIoT hub 110 and the IoT devices 101-102.

Embodiments which use public/private key pairs will first be described,followed by embodiments which use symmetric key exchange/encryptiontechniques. In particular, in an embodiment which uses PKI, a uniquepublic/private key pair is associated with each IoT device 101-102, eachIoT hub 110 and the IoT service 120. In one embodiment, when a new IoThub 110 is set up, its public key is provided to the IoT service 120 andwhen a new IoT device 101 is set up, it's public key is provided to boththe IoT hub 110 and the IoT service 120. Various techniques for securelyexchanging the public keys between devices are described below. In oneembodiment, all public keys are signed by a master key known to all ofthe receiving devices (i.e., a form of certificate) so that anyreceiving device can verify the validity of the public keys byvalidating the signatures. Thus, these certificates would be exchangedrather than merely exchanging the raw public keys.

As illustrated, in one embodiment, each IoT device 101, 102 includes asecure key storage 1401, 1403, respectively, for security storing eachdevice's private key. Security logic 1402, 1304 then utilizes thesecurely stored private keys to perform the encryption/decryptionoperations described herein. Similarly, the IoT hub 110 includes asecure storage 1411 for storing the IoT hub private key and the publickeys of the IoT devices 101-102 and the IoT service 120; as well assecurity logic 1412 for using the keys to perform encryption/decryptionoperations. Finally, the IoT service 120 may include a secure storage1421 for security storing its own private key, the public keys ofvarious IoT devices and IoT hubs, and a security logic 1413 for usingthe keys to encrypt/decrypt communication with IoT hubs and devices. Inone embodiment, when the IoT hub 110 receives a public key certificatefrom an IoT device it can verify it (e.g., by validating the signatureusing the master key as described above), and then extract the publickey from within it and store that public key in it's secure key store1411.

By way of example, in one embodiment, when the IoT service 120 needs totransmit a command or data to an IoT device 101 (e.g., a command tounlock a door, a request to read a sensor, data to beprocessed/displayed by the IoT device, etc) the security logic 1413encrypts the data/command using the public key of the IoT device 101 togenerate an encrypted IoT device packet. In one embodiment, it thenencrypts the IoT device packet using the public key of the IoT hub 110to generate an IoT hub packet and transmits the IoT hub packet to theIoT hub 110. In one embodiment, the service 120 signs the encryptedmessage with it's private key or the master key mentioned above so thatthe device 101 can verify it is receiving an unaltered message from atrusted source. The device 101 may then validate the signature using thepublic key corresponding to the private key and/or the master key. Asmentioned above, symmetric key exchange/encryption techniques may beused instead of public/private key encryption. In these embodiments,rather than privately storing one key and providing a correspondingpublic key to other devices, the devices may each be provided with acopy of the same symmetric key to be used for encryption and to validatesignatures. One example of a symmetric key algorithm is the AdvancedEncryption Standard (AES), although the underlying principles of theinvention are not limited to any type of specific symmetric keys.

Using a symmetric key implementation, each device 101 enters into asecure key exchange protocol to exchange a symmetric key with the IoThub 110. A secure key provisioning protocol such as the DynamicSymmetric Key Provisioning Protocol (DSKPP) may be used to exchange thekeys over a secure communication channel (see, e.g., Request forComments (RFC) 6063). However, the underlying principles of theinvention are not limited to any particular key provisioning protocol.

Once the symmetric keys have been exchanged, they may be used by eachdevice 101 and the IoT hub 110 to encrypt communications. Similarly, theIoT hub 110 and IoT service 120 may perform a secure symmetric keyexchange and then use the exchanged symmetric keys to encryptcommunications. In one embodiment a new symmetric key is exchangedperiodically between the devices 101 and the hub 110 and between the hub110 and the IoT service 120. In one embodiment, a new symmetric key isexchanged with each new communication session between the devices 101,the hub 110, and the service 120 (e.g., a new key is generated andsecurely exchanged for each communication session). In one embodiment,if the security module 1412 in the IoT hub is trusted, the service 120could negotiate a session key with the hub security module 1312 and thenthe security module 1412 would negotiate a session key with each device120. Messages from the service 120 would then be decrypted and verifiedin the hub security module 1412 before being re-encrypted fortransmission to the device 101.

In one embodiment, to prevent a compromise on the hub security module1412 a one-time (permanent) installation key may be negotiated betweenthe device 101 and service 120 at installation time. When sending amessage to a device 101 the service 120 could first encrypt/MAC withthis device installation key, then encrypt/MAC that with the hub'ssession key. The hub 110 would then verify and extract the encrypteddevice blob and send that to the device.

In one embodiment of the invention, a counter mechanism is implementedto prevent replay attacks. For example, each successive communicationfrom the device 101 to the hub 110 (or vice versa) may be assigned acontinually increasing counter value. Both the hub 110 and device 101will track this value and verify that the value is correct in eachsuccessive communication between the devices. The same techniques may beimplemented between the hub 110 and the service 120. Using a counter inthis manner would make it more difficult to spoof the communicationbetween each of the devices (because the counter value would beincorrect). However, even without this a shared installation key betweenthe service and device would prevent network (hub) wide attacks to alldevices.

In one embodiment, when using public/private key encryption, the IoT hub110 uses its private key to decrypt the IoT hub packet and generate theencrypted IoT device packet, which it transmits to the associated IoTdevice 101. The IoT device 101 then uses its private key to decrypt theIoT device packet to generate the command/data originated from the IoTservice 120. It may then process the data and/or execute the command.Using symmetric encryption, each device would encrypt and decrypt withthe shared symmetric key. If either case, each transmitting device mayalso sign the message with it's private key so that the receiving devicecan verify it's authenticity.

A different set of keys may be used to encrypt communication from theIoT device 101 to the IoT hub 110 and to the IoT service 120. Forexample, using a public/private key arrangement, in one embodiment, thesecurity logic 1402 on the IoT device 101 uses the public key of the IoThub 110 to encrypt data packets sent to the IoT hub 110. The securitylogic 1412 on the IoT hub 110 may then decrypt the data packets usingthe IoT hub's private key. Similarly, the security logic 1402 on the IoTdevice 101 and/or the security logic 1412 on the IoT hub 110 may encryptdata packets sent to the IoT service 120 using the public key of the IoTservice 120 (which may then be decrypted by the security logic 1413 onthe IoT service 120 using the service's private key). Using symmetrickeys, the device 101 and hub 110 may share a symmetric key while the huband service 120 may share a different symmetric key.

While certain specific details are set forth above in the descriptionabove, it should be noted that the underlying principles of theinvention may be implemented using various different encryptiontechniques. For example, while some embodiments discussed above useasymmetric public/private key pairs, an alternate embodiment may usesymmetric keys securely exchanged between the various IoT devices101-102, IoT hubs 110, and the IoT service 120. Moreover, in someembodiments, the data/command itself is not encrypted, but a key is usedto generate a signature over the data/command (or other data structure).The recipient may then use its key to validate the signature.

As illustrated in FIG. 15, in one embodiment, the secure key storage oneach IoT device 101 is implemented using a programmable subscriberidentity module (SIM) 1501. In this embodiment, the IoT device 101 mayinitially be provided to the end user with an un-programmed SIM card1501 seated within a SIM interface 1500 on the IoT device 101. In orderto program the SIM with a set of one or more encryption keys, the usertakes the programmable SIM card 1501 out of the SIM interface 500 andinserts it into a SIM programming interface 1502 on the IoT hub 110.Programming logic 1525 on the IoT hub then securely programs the SIMcard 1501 to register/pair the IoT device 101 with the IoT hub 110 andIoT service 120. In one embodiment, a public/private key pair may berandomly generated by the programming logic 1525 and the public key ofthe pair may then be stored in the IoT hub's secure storage device 411while the private key may be stored within the programmable SIM 1501. Inaddition, the programming logic 525 may store the public keys of the IoThub 110, the IoT service 120, and/or any other IoT devices 101 on theSIM card 1401 (to be used by the security logic 1302 on the IoT device101 to encrypt outgoing data). Once the SIM 1501 is programmed, the newIoT device 101 may be provisioned with the IoT Service 120 using the SIMas a secure identifier (e.g., using existing techniques for registeringa device using a SIM). Following provisioning, both the IoT hub 110 andthe IoT service 120 will securely store a copy of the IoT device'spublic key to be used when encrypting communication with the IoT device101.

The techniques described above with respect to FIG. 15 provide enormousflexibility when providing new IoT devices to end users. Rather thanrequiring a user to directly register each SIM with a particular serviceprovider upon sale/purchase (as is currently done), the SIM may beprogrammed directly by the end user via the IoT hub 110 and the resultsof the programming may be securely communicated to the IoT service 120.Consequently, new IoT devices 101 may be sold to end users from onlineor local retailers and later securely provisioned with the IoT service120.

While the registration and encryption techniques are described abovewithin the specific context of a SIM (Subscriber Identity Module), theunderlying principles of the invention are not limited to a “SIM”device. Rather, the underlying principles of the invention may beimplemented using any type of device having secure storage for storing aset of encryption keys. Moreover, while the embodiments above include aremovable SIM device, in one embodiment, the SIM device is not removablebut the IoT device itself may be inserted within the programminginterface 1502 of the IoT hub 110.

In one embodiment, rather than requiring the user to program the SIM (orother device), the SIM is pre-programmed into the IoT device 101, priorto distribution to the end user. In this embodiment, when the user setsup the IoT device 101, various techniques described herein may be usedto securely exchange encryption keys between the IoT hub 110/IoT service120 and the new IoT device 101.

For example, as illustrated in FIG. 16A each IoT device 101 or SIM 401may be packaged with a barcode or QR code 1501 uniquely identifying theIoT device 101 and/or SIM 1501. In one embodiment, the barcode or QRcode 1601 comprises an encoded representation of the public key for theIoT device 101 or SIM 1001. Alternatively, the barcode or QR code 1601may be used by the IoT hub 110 and/or IoT service 120 to identify orgenerate the public key (e.g., used as a pointer to the public key whichis already stored in secure storage). The barcode or QR code 601 may beprinted on a separate card (as shown in FIG. 16A) or may be printeddirectly on the IoT device itself. Regardless of where the barcode isprinted, in one embodiment, the IoT hub 110 is equipped with a barcodereader 206 for reading the barcode and providing the resulting data tothe security logic 1012 on the IoT hub 110 and/or the security logic1013 on the IoT service 120. The security logic 1012 on the IoT hub 110may then store the public key for the IoT device within its secure keystorage 1011 and the security logic 1013 on the IoT service 120 maystore the public key within its secure storage 1021 (to be used forsubsequent encrypted communication).

In one embodiment, the data contained in the barcode or QR code 1601 mayalso be captured via a user device 135 (e.g., such as an iPhone orAndroid device) with an installed IoT app or browser-based appletdesigned by the IoT service provider. Once captured, the barcode datamay be securely communicated to the IoT service 120 over a secureconnection (e.g., such as a secure sockets layer (SSL) connection). Thebarcode data may also be provided from the client device 135 to the IoThub 110 over a secure local connection (e.g., over a local WiFi orBluetooth LE connection).

The security logic 1002 on the IoT device 101 and the security logic1012 on the IoT hub 110 may be implemented using hardware, software,firmware or any combination thereof. For example, in one embodiment, thesecurity logic 1002, 1012 is implemented within the chips used forestablishing the local communication channel 130 between the IoT device101 and the IoT hub 110 (e.g., the Bluetooth LE chip if the localchannel 130 is Bluetooth LE). Regardless of the specific location of thesecurity logic 1002, 1012, in one embodiment, the security logic 1002,1012 is designed to establish a secure execution environment forexecuting certain types of program code. This may be implemented, forexample, by using TrustZone technology (available on some ARMprocessors) and/or Trusted Execution Technology (designed by Intel). Ofcourse, the underlying principles of the invention are not limited toany particular type of secure execution technology.

In one embodiment, the barcode or QR code 1501 may be used to pair eachIoT device 101 with the IoT hub 110. For example, rather than using thestandard wireless pairing process currently used to pair Bluetooth LEdevices, a pairing code embedded within the barcode or QR code 1501 maybe provided to the IoT hub 110 to pair the IoT hub with thecorresponding IoT device.

FIG. 16B illustrates one embodiment in which the barcode reader 206 onthe IoT hub 110 captures the barcode/QR code 1601 associated with theIoT device 101. As mentioned, the barcode/QR code 1601 may be printeddirectly on the IoT device 101 or may be printed on a separate cardprovided with the IoT device 101. In either case, the barcode reader 206reads the pairing code from the barcode/QR code 1601 and provides thepairing code to the local communication module 1680. In one embodiment,the local communication module 1680 is a Bluetooth LE chip andassociated software, although the underlying principles of the inventionare not limited to any particular protocol standard. Once the pairingcode is received, it is stored in a secure storage containing pairingdata 1685 and the IoT device 101 and IoT hub 110 are automaticallypaired. Each time the IoT hub is paired with a new IoT device in thismanner, the pairing data for that pairing is stored within the securestorage 685. In one embodiment, once the local communication module 1680of the IoT hub 110 receives the pairing code, it may use the code as akey to encrypt communications over the local wireless channel with theIoT device 101.

Similarly, on the IoT device 101 side, the local communication module1590 stores pairing data within a local secure storage device 1595indicating the pairing with the IoT hub. The pairing data 1695 mayinclude the pre-programmed pairing code identified in the barcode/QRcode 1601. The pairing data 1695 may also include pairing data receivedfrom the local communication module 1680 on the IoT hub 110 required forestablishing a secure local communication channel (e.g., an additionalkey to encrypt communication with the IoT hub 110).

Thus, the barcode/QR code 1601 may be used to perform local pairing in afar more secure manner than current wireless pairing protocols becausethe pairing code is not transmitted over the air. In addition, in oneembodiment, the same barcode/QR code 1601 used for pairing may be usedto identify encryption keys to build a secure connection from the IoTdevice 101 to the IoT hub 110 and from the IoT hub 110 to the IoTservice 120.

A method for programming a SIM card in accordance with one embodiment ofthe invention is illustrated in FIG. 17. The method may be implementedwithin the system architecture described above, but is not limited toany particular system architecture.

At 1701, a user receives a new IoT device with a blank SIM card and, at1602, the user inserts the blank SIM card into an IoT hub. At 1703, theuser programs the blank SIM card with a set of one or more encryptionkeys. For example, as mentioned above, in one embodiment, the IoT hubmay randomly generate a public/private key pair and store the privatekey on the SIM card and the public key in its local secure storage. Inaddition, at 1704, at least the public key is transmitted to the IoTservice so that it may be used to identify the IoT device and establishencrypted communication with the IoT device. As mentioned above, in oneembodiment, a programmable device other than a “SIM” card may be used toperform the same functions as the SIM card in the method shown in FIG.17.

A method for integrating a new IoT device into a network is illustratedin FIG. 18. The method may be implemented within the system architecturedescribed above, but is not limited to any particular systemarchitecture.

At 1801, a user receives a new IoT device to which an encryption key hasbeen pre-assigned. At 1802, the key is securely provided to the IoT hub.As mentioned above, in one embodiment, this involves reading a barcodeassociated with the IoT device to identify the public key of apublic/private key pair assigned to the device. The barcode may be readdirectly by the IoT hub or captured via a mobile device via an app orbrowser. In an alternate embodiment, a secure communication channel suchas a Bluetooth LE channel, a near field communication (NFC) channel or asecure WiFi channel may be established between the IoT device and theIoT hub to exchange the key. Regardless of how the key is transmitted,once received, it is stored in the secure keystore of the IoT hubdevice. As mentioned above, various secure execution technologies may beused on the IoT hub to store and protect the key such as SecureEnclaves, Trusted Execution Technology (TXT), and/or Trustzone. Inaddition, at 1803, the key is securely transmitted to the IoT servicewhich stores the key in its own secure keystore. It may then use the keyto encrypt communication with the IoT device. One again, the exchangemay be implemented using a certificate/signed key. Within the hub 110 itis particularly important to prevent modification/addition/removal ofthe stored keys.

A method for securely communicating commands/data to an IoT device usingpublic/private keys is illustrated in FIG. 19. The method may beimplemented within the system architecture described above, but is notlimited to any particular system architecture.

At 1901, the IoT service encrypts the data/commands using the IoT devicepublic key to create an IoT device packet. It then encrypts the IoTdevice packet using IoT hub's public key to create the IoT hub packet(e.g., creating an IoT hub wrapper around the IoT device packet). At1902, the IoT service transmits the IoT hub packet to the IoT hub. At1903, the IoT hub decrypts the IoT hub packet using the IoT hub'sprivate key to generate the IoT device packet. At 1904 it then transmitsthe IoT device packet to the IoT device which, at 1905, decrypts the IoTdevice packet using the IoT device private key to generate thedata/commands. At 1906, the IoT device processes the data/commands.

In an embodiment which uses symmetric keys, a symmetric key exchange maybe negotiated between each of the devices (e.g., each device and the huband between the hub and the service). Once the key exchange is complete,each transmitting device encrypts and/or signs each transmission usingthe symmetric key before transmitting data to the receiving device.

Embodiments of the invention may include various steps, which have beendescribed above. The steps may be embodied in machine-executableinstructions which may be used to cause a general-purpose orspecial-purpose processor to perform the steps. Alternatively, thesesteps may be performed by specific hardware components that containhardwired logic for performing the steps, or by any combination ofprogrammed computer components and custom hardware components.

As described herein, instructions may refer to specific configurationsof hardware such as application specific integrated circuits (ASICs)configured to perform certain operations or having a predeterminedfunctionality or software instructions stored in memory embodied in anon-transitory computer readable medium. Thus, the techniques shown inthe figures can be implemented using code and data stored and executedon one or more electronic devices (e.g., an end station, a networkelement, etc.). Such electronic devices store and communicate(internally and/or with other electronic devices over a network) codeand data using computer machine-readable media, such as non-transitorycomputer machine-readable storage media (e.g., magnetic disks; opticaldisks; random access memory; read only memory; flash memory devices;phase-change memory) and transitory computer machine-readablecommunication media (e.g., electrical, optical, acoustical or other formof propagated signals—such as carrier waves, infrared signals, digitalsignals, etc.). In addition, such electronic devices typically include aset of one or more processors coupled to one or more other components,such as one or more storage devices (non-transitory machine-readablestorage media), user input/output devices (e.g., a keyboard, atouchscreen, and/or a display), and network connections. The coupling ofthe set of processors and other components is typically through one ormore busses and bridges (also termed as bus controllers). The storagedevice and signals carrying the network traffic respectively representone or more machine-readable storage media and machine-readablecommunication media. Thus, the storage device of a given electronicdevice typically stores code and/or data for execution on the set of oneor more processors of that electronic device. Of course, one or moreparts of an embodiment of the invention may be implemented usingdifferent combinations of software, firmware, and/or hardware.

Throughout this detailed description, for the purposes of explanation,numerous specific details were set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however, toone skilled in the art that the invention may be practiced without someof these specific details. In certain instances, well known structuresand functions were not described in elaborate detail in order to avoidobscuring the subject matter of the present invention. Accordingly, thescope and spirit of the invention should be judged in terms of theclaims which follow.

What is claimed is:
 1. A system comprising: a system calibration moduleto collect signal strength data indicating signal strength between awireless device and a plurality of Internet of Things (IoT) devicesand/or IoT hubs within a user's home or business, the system calibrationmodule to associate the signal strength data with locations in theuser's home or business and store the association in a locationdatabase; a signal strength analysis module to determine a currentlocation of the wireless device by comparing the signal strength data inthe location database with current signal strength data indicatingcurrent signal strength between the wireless device and one or more ofthe plurality of IoT devices and/or IoT hubs; and a calibration appinstalled on the wireless device, the calibration app to communicatewith the system calibration module when collecting the signal strengthdata, the calibration app to instruct the user 1) to move to differentrooms and/or different positions within each room in the user's home orbusiness and 2) to provide an indication to the calibration app when theuser has arrived at each of the different rooms and/or differentpositions within each rooms.
 2. The system as in claim 1 wherein thecalibration app is to transmit current signal strength data between thewireless device and each of the plurality of IoT devices and/or IoT hubsupon providing the indication.
 3. The system as in claim 1 furthercomprising: an IoT hub on which the system calibration module and signalstrength analysis module are executed.
 4. The system as in claim 1wherein the location database comprises an identity of each location anda plurality of signal strength values associated with each location. 5.The system as in claim 4 wherein the plurality of signal strength valuescomprise received signal strength indicator (RSSI) values measuredbetween the wireless device and the plurality of IoT devices and/or IoThubs at each location.
 6. The system as in claim 5 wherein the signalstrength analysis module is to receive a current set of signal strengthvalues and compare those values with the signal strength data in thelocation database to determine the current location of the wirelessdevice.
 7. The system as in claim 6 wherein the signal strength analysismodule is to determine that the wireless device is in a particularlocation if the current signal strength values are within a specifiedrange of the signal strength values specified in the location database.8. The system as in claim 7 wherein the signal strength analysis moduleis to transmit one or more IoT device commands to control IoT devicesresponsive to the determination that the wireless device is in theparticular location.
 9. The system as in claim 8 wherein upondetermining that the wireless device is in a particular room, the signalstrength analysis module is to responsively turn on audio speakers inthe room and/or turn on lights in the room.
 10. The system as in claim 9wherein upon determining that the wireless device is in the particularroom, the signal strength analysis module is to responsively turn offaudio speakers in another room and/or turn off lights in the anotherroom.
 11. The system as in claim 1 wherein the signal strength analysismodule is to perform triangulation techniques to determine the currentlocation of the wireless device.
 12. The system as in claim 11 whereinthe triangulation techniques comprise measuring signal strength valuesbetween the wireless device and an IoT hub, the wireless device and anIoT device, and signal strength between the IoT device and the IoT hub.13. The system as in claim 1 wherein the signal strength data arecollected by the wireless device and transmitted to a first IoT hub. 14.The system as in claim 13 wherein the signal strength data are collectedfor wireless communication channels using a short distance wirelesscommunication standard and wherein the signal strength data aretransmitted from the wireless device to the first IoT hub using adifferent wireless communication standard.
 15. The system as in claim 14wherein the short distance wireless communication standard comprisesBluetooth Low Energy (BTLE) and the different wireless communicationstandard comprises a Wifi standard.
 16. A method comprising: collectingsignal strength data indicating signal strength between a wirelessdevice and a plurality of IoT devices and/or IoT hubs within a user'shome or business, wherein collecting signal strength data furthercomprises a calibration app on the wireless device communicating withthe IoT hub, the calibration app to instruct the user 1) to move todifferent rooms and/or different positions within each room in theuser's home or business and 2) to provide an indication to thecalibration app when the user has arrived at each of the different roomsand/or different positions within each rooms; associating the signalstrength data with locations in the user's home or business and storingthe association in a location database; and determining a currentlocation of the wireless device within the home or business by comparingthe signal strength data in the location database with current signalstrength data indicating current signal strength between the wirelessdevice and the plurality of IoT devices and/or IoT hubs.
 17. The methodas in claim 16 wherein the calibration app is to transmit current signalstrength data between the wireless device and each of the plurality ofIoT devices and/or IoT hubs upon providing the indication.
 18. Themethod as in claim 16 wherein the location database comprises anidentity of each location and a plurality of signal strength valuesassociated with each location.
 19. The method as in claim 18 wherein theplurality of signal strength values comprise received signal strengthindicator (RSSI) values measured between the wireless device and theplurality of IoT devices and/or IoT hubs at each location.
 20. Themethod as in claim 19 wherein determining a current location furthercomprises receiving a current set of signal strength values andcomparing those values with the signal strength data in the locationdatabase to determine the current location of the wireless device. 21.The method as in claim 20 wherein determining the current locationfurther comprises determining that the wireless device is in aparticular location if the current signal strength values are within aspecified range of the signal strength values specified in the locationdatabase.
 22. The method as in claim 21 further comprising transmittingone or more IoT device commands to control IoT devices responsive to thedetermination that the wireless device is in the particular location.23. The method as in claim 22 wherein upon determining that the wirelessdevice is in a particular room, responsively turning on audio speakersin the room and/or turning on lights in the room.
 24. The method as inclaim 23 wherein upon determining that the wireless device is in theparticular room, responsively turning off audio speakers in another roomand/or turning off lights in the another room.